Why static websites load so fast
A static website is a folder of finished HTML files. When someone visits, the server hands over the file exactly as stored, and that single fact explains most of the speed.
No waiting in line
Dynamic sites assemble every page on the spot: query the database, run the code, fill the template. Each step adds time. A static file skips all of it, so the main delay is the network itself. Static files also travel well. Because any server can host them, they can sit on a content delivery network with copies near the visitor, which cuts the distance a page has to cross.
Fewer parts, fewer failures
A static site has no database to crash, no plugins to conflict, no framework update at midnight. Security gets simpler too, since there is no admin panel to protect. For documentation, personal sites, landing pages and small business brochures, that sturdiness matters more than interactivity. The difference shows up first on slow connections, where every skipped server step is a second saved.
The tradeoffs
Anything with accounts, carts or search needs a server doing work, and static pages cannot do that on their own. Updating content means editing the file or rebuilding the site, which non technical writers may find awkward. The honest summary: if a page mostly needs to be read, static is hard to beat. If it needs to remember the visitor, some dynamic part is unavoidable, even if it lives elsewhere and feeds results into an otherwise static page.